Multifaceted approach to performantly enabling fileExists outside of the synchronize step in the emit host #25107
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…the synchronize step in the emit host
src/services/services.ts
Outdated
| // hostCache is captured in the closure for 'getOrCreateSourceFile' but it should not be used past this point. | ||
| // It needs to be cleared to allow all collected snapshots to be released | ||
| hostCache = undefined!; | ||
| hostCache = hostCache.thinCopy(); // The thin copy does not cache any snapshots, just their paths, so is relatively safe to hold onto longer-term |
Member
There was a problem hiding this comment.
I dont think we should do this since in most cases we wont need it? (eg --declaration is not enabled this is not needed.. Its not needed if there is no need to create refactoring)
Member
Author
There was a problem hiding this comment.
I'm fine with removing it if we're fine with not having the cache available at that point; we can always come back and add it back if we discover perf is an issue here anyway.
Member
Author
|
@sheetalkamat I've removed it - we can always go add it later if we decide the perf is an issue. |
| } | ||
|
|
||
| function getOrCreateSourceFileByPath(fileName: string, path: Path, _languageVersion: ScriptTarget, _onError?: (message: string) => void, shouldCreateNewSourceFile?: boolean): SourceFile | undefined { | ||
| Debug.assert(hostCache !== undefined); |
Member
There was a problem hiding this comment.
I think you do want to assert that hostCache !== undefined. That is getOrCreateSourceFileByPath should be called only when hostCache is not undefined.
sheetalkamat
approved these changes
Jun 22, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First, in
program, as @sheetalkamat suggested, we use the local caches if they have a result for the desired path. Since they still may not (ie, because the file isn't in the program, which is possibly the case when attempting to check paths for module specifiers), we also keep around a "thin" version of the host cache - effectively a host cache that doesn't contain any file contents, just metadata. (This way if the file is looked up for other reasons, that data is still there.) Finally, if both of those fail, we should hit disk (via the language server host).Fixes #25047
Deleting the host cache was a performance optimization so we didn't hold on to file contents for files we weren't actively using - this should retain that invariant, since we're replacing the cache with one with no content.